Ektron Reference |
An approval chain is a series of users or user groups who must approve content before it can be published on your Web site. When the last person in the chain approves content, it goes live.
Also, if a user deletes content, before it is removed from the CMS, it must pass through the approval chain.
When a new, edited, or deleted content is submitted to the approval chain, it is reviewed by users who may
Approval chains can be created for a folder or for content within a folder. If the approval chain for the folder and the content are different, the content approval chain overrides the folder approval chain.
The chart below illustrates the approval process.
You can approve, edit, or decline all content submitted to you from the approval folder.
The CMS can automatically send email notification, informing users that content workflow events have either taken place or are requested of them. As examples
The list of automatic emails and directions for customizing their content are described in Customizing Ektron email.
An approval chain can include any number of users or user groups. However, only users or user groups with read-only or higher permission to the folder or content item can be added to the approval chain. See Also: Managing Folder Permissions
NOTE: If you assign a user group to an approval chain, only one member of the group needs to approve the content, not all members.Also, if a user appears in an approval chain twice (both as a user and part of a user group), the approval chain skips the second approval because the user has already approved the content.
You can set up an approval chain for a content folder or a content item as well as a language. See Also: Multi-Language Approval Chains
Finally, the Approval Method determines if content must be approved by all users in the chain, or only users higher up the chain than the one making the edits.
Prerequisite: Only members of the Administrators group and users assigned to the Folder User Admin Role screen can modify the approval chain See Also: Defining Roles
An approval chain lets you control how and when your Web site is updated. For example, if your Webmaster needs to approve every new content item or update of an existing item, he would be last user in every approval chain and exert total control over the site.
Alternatively, you could set up a less centralized organization, where each department head controls his section. To accommodate this, set up an approval chain for each department, and assign the department head as the last person in the chain.
On the opposite extreme, you can delete the approval chain for a content item or folder. In this case, every item in that folder is published as soon as a user submits it for publication.
An approval chain’s inheritance is determined by the corresponding permission table. If a folder’s permission table inherits settings from its parent folder, that folder’s approval chain also inherits. To learn about enabling and disabling permission table inheritance, see Inheriting Permissions.
The Approval Chain screen only displays its inheritance status; it does not let you set it.
Prerequisite: Only members of the Administrators group and users assigned to the Folder User Admin Role screen can modify the approval chain See Also: Defining Roles
Before you can create or edit an approval chain, you must access the View screen.
To view a folder’s approval chain:
This screen shows the following information about the approval chain.
From this screen, you can perform these actions:
To add a user or user group to the approval chain:
Prerequisite: Only users and user groups with permissions to the folder appear. See Adding a User or User Group to the Permissions Table for more information.
Best Practice Ektron suggests assigning user groups to the approval chain, as opposed to individual users. In this way, if someone is out of the office for a day, another group member can approve the content. |
NOTE: If you assign a user group to an approval chain, any member of the group can approve the content, not all members.
After you assign approvers to a folder, you may want to adjust the approval order. Place the user or group with final review at the end of the approval chain (that is, the highest number).
For example, if you have a content contributor whose edits must be approved by a department head, and the Webmaster has final review of all content, the approval order would look like this.
To edit the approval order:
NOTE: If a user in an approval chain is deleted from the permissions table, he or she is automatically deleted from the approval chain.
To delete a user or user group from an approval chain:
You can change the approval chain for a specific content item. Use the View Content screen's Approvals button to do this.
Prerequisites:
You can perform the same actions on the content’s approval chain that you can perform on a folder's. See Performing Actions from the Approvals Screen.
A toolbar at the top of the screen lists tasks you can perform on the content.
Button | Name | Result of Clicking |
---|---|---|
Publish |
Accept changes to the content and publish it to the site. NOTE: If there is another approver in the content’s approval chain, this is replaced by a SUBMIT button. If you click Publish but the content item has an incomplete task assigned to another user, the content cannot be published. Instead, the following error message appears.
The user to whom the task is assigned must complete it before you can publish the content. |
|
Decline |
Reject changes and keep current version of content live on Web site. You are prompted to enter a comment that provides a reason for the decline. The author who made the change is notified by email of the decline. The content inserted by the last editor remains in the file. If you do not want it to remain, choose the Edit option. |
|
Edit | Check out content and change it if desired. | |
|
View Published/Staged | Toggle between published and submitted versions of content. This can help you compare versions. |
View Diff |
View differences between the version awaiting approval and the published content. See Also: Comparing Versions of Content |
|
Back | Return to previous screen. |
To approve several submitted content items without reviewing them:
The approval chain begins when a content contributor submits a new or edited content. If email is enabled, an email is sent to the next approver in the approval chain.
The following example follows a typical content block from creation to publication. Three users make up this approval chain.
Each user has different permissions that correspond to their roles.
The first step is to create content. To create new content, follow these steps.
NOTE: Emails are only sent if your administrator enables them.
The content contributor, Sports Writer, has completed his role in the approval chain but continues to receive emails notifying him of changes in the content’s status.
After Sports Writer submits the content, the first user in the approval chain, Sports Editor, receives an email stating content needs his approval. He can change and approve the content or decline it.
Sports Editor logs into Ektron, navigates to his desktop, where he sees the Content Awaiting Approval panel.
He clicks the View All link and sees all content awaiting his approval.
The approvals folder window displays information such as title, who submitted it, go live date, etc. The Sports editor clicks the submitted content.
The View Content Awaiting Approvals window appears listing all information necessary to decide whether to approve or decline the content.
At the approval window, the Sports Editor has these options.
For demonstration purposes, we choose Publish.
After the content is approved, the next approver in the approval chain receives an email saying that the content is ready for approval.
EditorInChief logs in to Ektron and accesses his Workarea. The Workarea has an Approval folder with the content awaiting his approval. EditorInChief navigates through the Approval folder until he finds the content Red Sox win World Series.
From this window, EditorInChief can view information about the content, including title, go live date, user who created it, etc. He then clicks the content he wants to approve.
This window is similar to the previous approver’s but includes a Publish button at the top of the screen. The EditorInChief has a publish button (instead of a submit button) because he is the last approver in the approval chain. When he approves the content, it is published to the Web site.
Like the Sports editor, the EditorInChief has the following options:
Edit —Invokes the editor. The approver changes the content.
After reviewing the content, the EditorInChief decides it is great and publishes it. At this point, the content becomes live on the Web site, and the approval chain is complete.
The user who created the content receives an email notifying him that it was published.
The Approval Method determines if content must be approved by all users in the chain, or only users higher up in the chain than the user making the edits. The approval method only affects the approval process if the person submitting content for publishing is a member of the approval chain.
Two approval methods are available.
For example, assume the approval chain, user or user group name and approval order, is set as follows:
If the Approval Method is Force All Approvers, and the Department Head submits content, the content must be approved by the content contributor, then the department head, and the Webmaster before it is published.
If the Approval Method is Do Not Force All Approvers, and the Department Head submits content, the content must only be approved the Webmaster before it is published.
By default, the approval method is set to Do Not Force All Approvers. To change the approval method for a content folder or item, follow these steps.
Ektron Version 8.5, Doc. Rev. 2.0 (Dec. 2011)
Visit the Ektron Dev Center at http://dev.ektron.com 1–866–4–EKTRON
Ektron Documentation, © 2011 Ektron, Inc.